home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d16
/
win_uae.arc
/
UNRECOVR.WIN
< prev
Wrap
Text File
|
1990-08-20
|
5KB
|
127 lines
Q63359 Unrecoverable Application Error in Windows 3.00
Microsoft Windows 3 Retail Product (WIN3)
3.00
MS-DOS
Summary:
This article contains information on potential causes of the Microsoft
Windows version 3.00 error message:
Unrecoverable Application Error
Terminating current application
This error occurs only in standard- and enhanced-mode Windows 3.00. It
indicates that a Windows application has caused a protection violation
(that is, an application has written to a memory space to which it
does not have access, potentially corrupting other code in that area
of memory).
If you receive this error, the Windows 3.00 system will be unstable
until you exit Windows, reboot the system, and restart Windows. After
one application causes such an error, memory will be corrupted. This
could cause other applications to subsequently receive the same error,
even though they are not actually the cause of the problem.
The following are possible causes for an unrecoverable application
error:
1. You are running an application that was designed for Windows
versions 2.00, 2.03, 2.10, and 2.11 under Windows 3.00 in standard
or enhanced mode.
If an application has not been properly designed to function
correctly under Windows 3.00 protected modes, it will cause an
error. If an application is designed for Windows versions 2.00,
2.03, 2.10, and 2.11, it will generate a dialog box when executed
that advises you of this error. Such applications should be run only
under Windows 3.00 real mode as the dialog box suggests.
2. You have selected an incorrect machine and/or network while using
the Setup program.
Some machines and networks require you to override the default
detection made by Windows 3.00 Setup and make a specific selection.
If the correct selection is not made, Windows will not operate
correctly.
Machines that must be specifically selected in Windows
Setup include the following:
All 80386- and 80486-based AST machines
All 80386-based Zenith machines
All Hewlett-Packard machines
Everex Step 386/25
NCR PC 386SX
NCR PC 925
NEC PowerMate SX Plus
NEC ProSpeed 386
Toshiba 1600
Toshiba 5200
Networks that must be specifically selected in Windows Setup include
the following:
3Com 3+Open LAN Manager (XNS only)
3Com 3+Share
Banyan VINES version 4.0
LAN Manager versions 1.x (or 100-percent compatible)
IBM PC LAN program
If you did not choose your machine or network specifically during
Setup, you should exit Windows and run the DOS version of Setup
from the WINDOWS directory. This will allow you to make the proper
selection without having to completely reinstall Windows 3.00.
3. You have incompatible TSRs (terminate-and-stay-resident programs)
or unsupported network drivers in the CONFIG.SYS or AUTOEXEC.BAT
files.
Temporarily remove all suspect drivers and TSR programs
to bring the system to a minimum configuration for
testing purposes. If this eliminates the problem, then
the problem was caused by one of the drivers or TSRs
that was removed. Replace the removed lines one by one
until the problem reappears, thus showing which line
was causing the problem.
4. You have a page-mapping conflict in enhanced mode.
This cause applies only to enhanced-mode Windows. Test the problem
under standard mode by running Windows with the WIN /S parameter.
If the problem does not occur in standard mode, it may be a
page-mapping conflict in the adapter segment area of memory
(between A000 and EFFF hexadecimal). Edit the SYSTEM.INI file with
Notepad or SYSEDIT and insert the following line in the [386ENH]
section:
EMMExclude=A000-EFFF
This will exclude the entire adapter segment from mapping. This
line is not case sensitive. If inserting this line solves the
problem, you may want to determine the position of all hardware
adapters in the adapter segment and exclude them specifically
rather than excluding the entire region. Multiple EMMExclude lines
may be used if necessary. If you are using a Micro Channel (MCA)
bus machine such as an IBM PS/2, you may determine the adapter
location by booting with the machine's Reference Disk. If you are
using a standard (ISA) bus machine, consult your adapter
documentation and/or manufacturer's technical support service for
information on memory locations used, if any.
5. You have the incorrect DOS version.
Machines should have the proper DOS version for their hardware
type. OEM (Original Equipment Manufacturer) versions of DOS such as
COMPAQ DOS or IBM PC-DOS should not be used except on their
respective OEM hardware platforms (that is, COMPAQ DOS only on
COMPAQ machines, IBM PC-DOS only on IBM machines).
On other machines, the proper DOS should be determined by the
following rule: If the manufacturer has an OEM version of DOS, it
should be used. If the manufacturer does not have an OEM version of
DOS, generic Microsoft MS-DOS should be used.
COPYRIGHT Microsoft Corporation, 1990.
Updated 90/07/13 04:30